Keep real ThingsBoard verification isolated - #127

Description

Isolate the context-test fixture

Mark the test-only JpaAttributeDao fixture lazy. The context tests exercise bean-definition selection and withdrawal; they do not exercise the host DAO itself. Against genuine ThingsBoard 4.3.1.2 types, eager construction also requires host-application collaborators such as jpaExecutorService, which this isolated module test intentionally does not bootstrap.

This changes no production code. The verification guide now states the resulting proof boundary explicitly: these context assertions cover definition selection, while host-application compatibility requires a separate live ThingsBoard deployment.

Refresh genuine-interface verification evidence

Update VERIFYING-AGAINST-THINGSBOARD.md with the current genuine-type surface and test counts after #125:

• compile-only build: 59 source files
• genuine ThingsBoard 4.3.1.2 build: 19 source files
• unit tests: 204 passed
• Docker integration tests: 58 passed
• failures, errors, and skipped tests: 0

The built module contains no org/thingsboard classes.

This PR has:

• been self-reviewed.
• added documentation for the modified test behavior.
• added comments explaining the intent of the test fixture.
• been tested against genuine ThingsBoard 4.3.1.2 types and a real IoTDB 2.0.8 Testcontainer.

Key changed classes and documents

• AttributesDaoConflictGuardTest
• VERIFYING-AGAINST-THINGSBOARD.md